CD ROM Paradise Collection 4/CD ROM Paradise Collection 4 1995 Nov.iso/comms_w/pboy190.zip/SAMPLE.ZIP/0000046.MSG

Text File | 1994-03-06 | 6KB | 126 lines

#! rnews 841
Newsgroups: comp.os.ms-windows.nt.misc
Path: netnews.upenn.edu!msuinfo!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!EU.net!uknet!cix.compulink.co.uk!aroby
From: [e-mail] ("Anthony Roby")
Subject: Re: PPP and SLIP for NT
Message-ID: <[e-mail]>
Organization: @home
References: <2lad21$[e-mail]>
Date: Sun, 6 Mar 1994 11:44:36 GMT
X-News-Software: Ameol
Lines: 8

Connect to do what ?  You can connect using the Remote Access Services
which allow your laptop to act as though it was connected directly to the
LAN, albeit via a slow link.

-------------------------------------------------------------------------
Anthony Roby         [e-mail]
7 Delcombe Avenue    [e-mail]
Worcester Park                 Surrey    ENGLAND    Phone [phone]
#! rnews 889
Newsgroups: comp.os.ms-windows.nt.misc
Path: netnews.upenn.edu!msuinfo!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!EU.net!uknet!cix.compulink.co.uk!aroby
From: [e-mail] ("Anthony Roby")
Subject: Re: Listing Devices In Windows NT
Message-ID: <[e-mail]>
Organization: @home
References: <[e-mail]>
Date: Sun, 6 Mar 1994 12:35:50 GMT
X-News-Software: Ameol
Lines: 11

> We are writing a NT device driver and would like some clarifications...
> 1) I would like to look at the list of devices in NT. > Can I somehow
do "ls \device\*"?

Use the devices program in the Resource Kit.

Anthony
-------------------------------------------------------------------------
Anthony Roby         [e-mail]
7 Delcombe Avenue    [e-mail]
Worcester Park                 Surrey    ENGLAND    Phone [phone]
#! rnews 4418
Newsgroups: comp.os.ms-windows.nt.misc
Path: netnews.upenn.edu!msuinfo!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!EU.net!uknet!cix.compulink.co.uk!aroby
From: [e-mail] ("Anthony Roby")
Subject: Re: Windows NT Authentication
Message-ID: <[e-mail]>
Organization: @home
References: <[e-mail]>
Date: Sun, 6 Mar 1994 12:35:53 GMT
X-News-Software: Ameol
Lines: 70

> Hi ho--
> > I'm doing a paper for my grad class on NT's object manager, and I was
> tryingto get more information on the authentication mechanism used in
> thedistributed security version of NT.  It'd be nice if it were some
> form of
> public key mechanism.
> > If anyone know (or knows someone who knows), please post or let me
know.
> --
> # [e-mail] --------------------------- Eric
> Stenson #

The following is more about the logon process than distributed security.
In the distributed model, the client machine asks the domain server for a
security challenge for a particular user.  I think it then uses this
challenge to encrypt the userid and password and send to the domain
controller (ie avoiding sending the password over the network as readable
text).

In Windows NT, local logon at the attached keyboard and screen occurs
through the interaction of WinLogon (logon process), the Local Security
Authority (LSA), one or more authentication packages, and the Security
Account Manager (SAM). It is the LSA that authenticates a user through
the services provided to logon processes and authentication packages.

Logon processes are special processes that intercept specific keystroke
combinations, called Secure Access Sequences (SAS), from log on devices,
and then prompt for device-specific information from the user who is
attempting to logon. WinLogon is the process that intercepts logon
requests from the keyboard. The WinLogon process makes calls to LSA and
the Windows NT authentication package to authenticate the user attempting
to log on.  If the user is authenticated, the logon process activates a
logon shell on behalf of the user.

Authentication packages are dynamically linked libraries that perform
authentication checks specific to the kind of information the package
expects. A package used to authenticate an Automatic Teller Machine (ATM)
may take a user name and identification number as its credentials.

Additional packages could include a Novell or Banyan specific package as
an example, or other packages provided by OEMs or ISVs. At boot time, LSA
looks in its policy database for the list of authentication packages
available on the machine and links to these packages.

Any supplemental authentication package that has registered itself with
the LSA will be called after the Windows NT authentication package is
called. Users can then provide whatever credentials the supplemental
package expects. The Windows NT authentication package expects a username
and password. If the supplemental package also expects a username and
password, users can log on to additional environments, such as NetWare,
with a single username and password.
The practical realization of this ability is aptly demonstrated with the
Microsoft NetWare Workstation Compatible Services (NWCS). Before a users
can use a file, application, or print queue on a NetWare server, they
must have an account on the server. The NetWare server account contains
users credentials, which are the username and password. By default,
Windows NT supplies the username and password that were used by users
when they logged on to Windows NT as the credentials it sends to the
NetWare server. It is best that users keep their username and password on
NetWare servers the same as those that they use when logging on to
Windows NT. This allows users to use NetWare servers without having to
supply another username and password. It also makes it easier for network
administrators to coordinate user accounts. Users will be prompted to
supply credentials only if their username and password on the NetWare
server are not the same as their username and password in Windows NT.

-------------------------------------------------------------------------
Anthony Roby         [e-mail]
7 Delcombe Avenue    [e-mail]
Worcester Park                 Surrey    ENGLAND    Phone [phone]